FOUR-31920: Add rollback CI spike for LDAP regression#8873
Closed
eiresendez wants to merge 1 commit into
Closed
Conversation
|
Contributor
|
QA server K8S was successfully deployed https://ci-dfe8bc090c.engk8s.processmaker.net |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.





Issue & Reproduction Steps
LDAP synchronization is partially processing results after the recent dependency updates. In the affected build, LDAP sync imports configured groups but does not import departments or existing users as expected.
This PR is a diagnostic rollback spike for FOUR-31920. It is intended to determine whether reverting the Laravel dependency bump introduced by #8851 resolves the LDAP regression reported in FOUR-31832.
To reproduce, deploy this branch with the CI/CD deploy server and run the LDAP synchronization scenario from FOUR-31832:
Solution
^13.13back to^13.0.composer.lockto downgrade the dependency set affected by the Laravel bump, including Laravel, Guzzle, and PSR-7.How to Test
Local validation already performed:
composer install --dry-run --no-interactioncomposer validatepassed with existing repository warningsRelated Tickets & Packages
ci:deploy